W3C</abbr></a><sup>®</sup> (<a href="http://www.lcs.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.inria.fr/"><abbr xml:lang="fr" title=
"Institut National de Recherche en Informatique et Automatique">INRIA</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href=
"http://www.w3.org/Consortium/Legal/copyright-documents-19990405">document use</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-software-19980720">software licensing</a> rules apply.</p>
<hr />
</div>
<h2><a id="abstract"></a> Abstract</h2>
<p>This Recommendation defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML [<a href="#ref_xhtml_modularization">XHTMLMOD</a>]. The
purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the
deprecated, legacy functionality of HTML 4 [<a href="#ref_html4">HTML4</a>] that was brought forward into the XHTML 1.0 [<a href="#ref_xhtml1">XHTML1</a>] document types. This document type is
essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this
document type. These other facilities are available through modules defined in Modularization of XHTML, and document authors are free to define document types based upon XHTML 1.1 that use these
facilities (see [<a href="#ref_xhtml_modularization">XHTMLMOD</a>] for information on creating new document types).</p>
<h2><a id="status"></a> Status of this document</h2>
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the
W3C.</em></p>
<p>This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference
material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This
enhances the functionality and interoperability of the Web.</p>
<p>This document has been produced by the <a href="http://www.w3.org/MarkUp/Group/">W3C HTML Working Group</a> (<em><a href="http://cgi.w3.org/MemberAccess/AccessRequest">members only</a></em>) as
part of the <a href="http://www.w3.org/MarkUp/">W3C HTML Activity</a>. The goals of the HTML Working Group are discussed in the <a href="http://www.w3.org/MarkUp/2000/Charter">HTML Working Group
charter</a>. The W3C staff contact for work on HTML is <a href="mailto:mimasa@w3.org">Masayasu Ishikawa</a>.</p>
<p>Public discussion of HTML takes place on <a href="mailto:www-html@w3.org">www-html@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/www-html/">archive</a>). To subscribe send an email to
<a href="mailto:www-html-request@w3.org">www-html-request@w3.org</a> with the word <em>subscribe</em> in the subject line.</p>
<p>Please report errors in this document to <a href="mailto:www-html-editor@w3.org">www-html-editor@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/www-html-editor/">archive</a>). The list
of <a href="http://www.w3.org/2001/05/REC-xhtml11-20010531-errata">known errors</a> in this specification is available at http://www.w3.org/2001/05/REC-xhtml11-20010531-errata.</p>
<p>The English version of this specification is the only normative version. Information about <a href="http://www.w3.org/MarkUp/translations">translations of this document</a> is available at
http://www.w3.org/MarkUp/translations.</p>
<p>A list of current W3C Recommendations and other technical documents can be found at <a href="http://www.w3.org/TR">http://www.w3.org/TR</a>.</p>
<p>With the introduction of the XHTML family of modules and document types, the W3C has helped move the Internet content-development community from the days of malformed, non-standard markup into the
well formed, valid world of XML [<a href="#ref_xml">XML</a>]. In XHTML 1.0, this move was moderated by a goal of providing for easy migration of existing, HTML 4 (or earlier) based content to XHTML
and XML. With the advent of the XHTML modules defined in Modularization of XHTML, the W3C has removed support for deprecated elements and attributes from the XHTML family. These elements and
attributes were largely presentation oriented functionality that is better handled via style sheets or client-specific default behavior.</p>
<p>Going forward, XHTML family document types will be based upon this new, more structural functional collection. In this specification, the W3C's HTML Working Group has defined an initial document
type based solely upon modules. This document type is designed to be portable to a broad collection of client devices, and applicable to the majority of Internet content. Content developers who base
their content upon the functionality expressed in this specification can be confident that it will be consistently portable across XHTML family conforming user agents.</p>
<p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <a href="#ref_RFC2119">
<p>This version of XHTML provides a definition of strictly conforming XHTML documents, which are restricted to elements and attributes from the XHTML namespace.</p>
<p>A strictly conforming XHTML 1.1 document is a document that requires only the facilities described as mandatory in this specification. Such a document must meet all the following criteria:</p>
<ol>
<li>
<p>The document must conform to the constraints expressed in <a href="#a_xhtml11_dtd">Appendix C</a>.</p>
</li>
<li>
<p>The root element of the document must be <code><html></code>.</p>
</li>
<li>
<p>The root element of the document must designate the XHTML namespace using the <code>xmlns</code> attribute <a href="#ref_xmlns">[XMLNAMES]</a>. The namespace designator for XHTML is
"<code>http://www.w3.org/1999/xhtml</code>".</p>
</li>
<li>
<p>There must be a DOCTYPE declaration in the document prior to the root element. If present, the public identifier included in the DOCTYPE declaration must reference the DTD found in <a href=
"#a_xhtml11_dtd">Appendix C</a> using its Formal Public Identifier. The system identifier may be modified appropriately.</p>
<pre>
<!DOCTYPE
html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
</pre>
</li>
</ol>
<p>Here is an example of an XHTML 1.1 document.</p>
<p>Moved to <a href="http://vlib.org/">vlib.org</a>.</p>
</body>
</html>
</pre>
</div>
<p>Note that in this example, the XML declaration is included. An XML declaration like the one above is not required in all XML documents. XHTML document authors are strongly encouraged to use XML
declarations in all their documents. Such a declaration is required when the character encoding of the document is other than the default UTF-8 or UTF-16.</p>
<h2><a id="uaconf">2.2.</a> User Agent Conformance</h2>
<p>A conforming user agent must meet all user agent conformance requirements defined in [<a href="#ref_xhtml_modularization">XHTMLMOD</a>].</p>
<!--OddPage-->
<h1><a id="s_doctype">3.</a> The XHTML 1.1 Document Type</h1>
<p>This section is <em>normative</em>.</p>
<p>The XHTML 1.1 document type is a fully functional document type with rich semantics. It is not, however, as varied in functionality as the XHTML 1.0 Transitional or Frameset document types. These
document types defined many presentational components that are better handled through style sheets or other similar mechanisms. Moreover, since the XHTML 1.1 document type is based exclusively upon
the facilities defined in the XHTML modules [<a href="#ref_xhtml_modularization">XHTMLMOD</a>], it does not contain any of the deprecated functionality of XHTML 1.0 nor of HTML 4. Despite these
exceptions, or perhaps because of them, the XHTML 1.1 document type is a solid basis for future document types that are targeted at varied user agent environments.</p>
<p>The XHTML 1.1 document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML"
[<a href="#ref_xhtml_modularization">XHTMLMOD</a>]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the
on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".</p>
<p>XHTML also uses the Ruby Annotation module as defined in [<a href="#ref_ruby">RUBY</a>]:</p>
<dl>
<dt>Ruby Annotation Module</dt>
<dd><code>ruby, rbc, rtc, rb, rt, rp</code></dd>
</dl>
<p>There are no additional definitions required by this document type. An implementation of this document type as an XML DTD is defined in <a href="#a_xhtml11_dtd">Appendix C</a>.</p>
<!--OddPage-->
<h1><a id="a_changes">A.</a> Changes from XHTML 1.0 Strict</h1>
<p>This appendix is <em>informative</em>.</p>
<p>This Appendix describes the differences between XHTML 1.1 and XHTML 1.0 Strict. XHTML 1.1 represents a departure from both HTML 4 and XHTML 1.0. Most significant is the removal of features that
were deprecated. In general, the strategy is to define a markup language that is rich in structural functionality, but that relies upon style sheets for presentation.</p>
<p>The differences can be summarized as follows:</p>
<ol>
<li>On every element, the <tt>lang</tt> attribute has been removed in favor of the <tt>xml:lang</tt> attribute (as defined in [<a href="#ref_xhtml_modularization">XHTMLMOD</a>]).</li>
<li>On the <tt>a</tt> and <tt>map</tt> elements, the <tt>name</tt> attribute has been removed in favor of the <tt>id</tt> attribute (as defined in [<a href=
"#ref_xhtml_modularization">XHTMLMOD</a>]).</li>
<li>The "<tt>ruby</tt>" collection of elements has been added (as defined in [<a href="#ref_ruby">RUBY</a>]).</li>
<dd><cite><a href="http://www.w3.org/TR/1999/REC-html401-19991224">HTML 4.01 Specification</a></cite>, W3C Recommendation, Dave Raggett, Arnaud Le Hors, Ian Jacobs, 24 December 1999.<br />
<dd><cite><a href="http://www.w3.org/TR/2000/REC-xhtml1-20000126">XHTML 1.0: The Extensible HyperText Markup Language</a></cite>, W3C Recommendation, Steven Pemberton, et al., 26 January 2000.<br />
<dd><cite><a href="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410">Modularization of XHTML</a></cite>, W3C Recommendation, Murray Altheim, et al., 10 April 2001<br />
<dd><cite><a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0 (Second Edition)</a></cite>, W3C Recommendation, Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, Eve
<dd><cite><a href="http://www.w3.org/TR/2001/REC-ruby-20010531">Ruby Annotation</a></cite>, W3C Recommendation, Marcin Sawicki, et al., 31 May 2001.<br />
<dd>"<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to indicate requirement levels</a></cite>", RFC 2119, S. Bradner, March 1997.<br />
Available at: http://www.ietf.org/rfc/rfc2119.txt</dd>
<dd>"<cite><a href="http://www.w3.org/TR/1999/REC-xml-names-19990114">Namespaces in XML</a></cite>", W3C Recommendation, Tim Bray, Dave Hollander, Andrew Layman, 14 January 1999.<br />
Available at: http://www.w3.org/TR/1999/REC-xml-names-19990114</dd>
</dl>
<!--OddPage-->
<h1><a id="a_xhtml11_dtd">C.</a> XHTML 1.1 Document Type Definition</h1>
<p>This appendix is <em>normative</em>.</p>
<h2><a id="a_xhtml11_catalog">C.1.</a> SGML Open Catalog Entry for XHTML 1.1</h2>
<p>This section contains the SGML Open Catalog-format definition [<a href="#ref_catalog">CATALOG</a>] of the XHTML 1.1 FPI.</p>
<p>This section contains the driver for the XHTML 1.1 document type implementation as an XML DTD. It relies upon XHTML module implementations defined in [<a href=
"#ref_xhtml_modularization">XHTMLMOD</a>] and in [<a href="#ref_ruby">RUBY</a>].</p>
<p>An XHTML Family Document Type (such as XHTML 1.1) must define the content model that it uses. This is done through a separate content model module that is instantiated by the XHTML Modular
Framework. The content model module and the XHTML 1.1 Driver (above) work together to customize the module implementations to the document type's specific requirements. The content model module for
<!-- %Block.mix; includes all block elements plus %Misc.class;
-->
<!ENTITY <span class="entity">% Block.mix</span>
"%Heading.class;
| %List.class;
| %Block.class;
%Misc.class;"
>
<!-- ................ All Content Elements .................. -->
<!-- %Flow.mix; includes all text content, block and inline
-->
<!ENTITY <span class="entity">% Flow.mix</span>
"%Heading.class;
| %List.class;
| %Block.class;
| %Inline.class;
%Misc.class;"
>
<!-- end of xhtml11-model-1.mod -->
</pre>
<!--OddPage-->
<h1><a id="a_acks">D.</a> Acknowledgements</h1>
<p>This appendix is <em>informative</em>.</p>
<p>This specification was prepared by the <acronym title="World Wide Web Consortium">W3C</acronym> <acronym title="HyperText Markup Language">HTML</acronym> Working Group. The members at the time of
publication were:</p>
<ul>
<li>Steven Pemberton, <acronym title="Centrum voor Wiskunde en Informatica" xml:lang="nl">CWI</acronym> (<acronym title="HyperText Markup Language">HTML</acronym> Working Group Chair)</li>
